Multi-Activity Platform and Interface

ABSTRACT

A multi-activity system may be configured to receive, upload, synchronize and process data for a variety of different activity types and/or recorded using multiple types of activity monitoring devices. In one example, an application interface may be defined with a multiple functions that are each useable by various types of devices and for processing multiple types of data. Additionally or alternatively, data for different activity types and/or recorded using different types of monitoring devices may be processed differently. Synchronization of data may further be handled on a device-by-device basis, device-type basis and/or activity-type basis using various tracking parameters.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. patentapplication Ser. No. 13/744,988, entitled “MULTI-ACTIVITY PLATFORM ANDINTERFACE,” and filed Jan. 18, 2013, which claims priority to U.S.Provisional Application Ser. No. 61/588,610, entitled “MULTI-ACTIVITYPLATFORM AND INTERFACE,” and filed on Jan. 19, 2012. The contents of theaforementioned applications are hereby incorporated by reference intheir entirety.

BACKGROUND

Exercise and fitness have become increasingly popular and the benefitsfrom such activities are well known. Various types of technology havebeen incorporated into fitness and other athletic activities. Forexample, a wide variety of portable electronic devices are available foruse in fitness activities, such as MP3 or other audio players, radios,portable televisions, DVD players, or other video playing devices,watches, GPS systems, pedometers, mobile telephones, pagers, beepers,etc. Many fitness enthusiasts or athletes use one or more of thesedevices when exercising or training to keep them entertained, record andprovide performance data or to keep them in contact with others, etc.

BRIEF SUMMARY

The following presents a general summary of aspects of the disclosure inorder to provide a basic understanding of at least some of its aspects.This summary is not an extensive overview. It is not intended toidentify key or critical elements or to delineate the scope. Thefollowing summary merely presents some concepts of the invention in ageneral form as a prelude to the more detailed description providedbelow.

Aspects described herein provide activity data recording, on-linecommunities and interfaces between activity monitoring and trackingdevices and systems supporting multiple different types of activities.Additionally or alternatively, the various aspects described hereinprovide for distinguishing activity data and information based on a typeof device through which the activity data was recorded. Still further,activity data from multiple types of activity types, devices and devicetypes and activity sessions may be aggregated toward a single goal. Inthis manner, goals providing motivation to perform activities (includingfitness programs, sports, and other types of physical activity andathletic activity) might no longer limit users to a single activity ordevice for a particular goal.

Other aspects and features are described throughout the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 illustrates an example system in which various features discussedherein may be included and/or implemented.

FIG. 2 illustrates an example device in which various features discussedherein may be included and/or implemented.

FIG. 3 illustrates another example device in which various featuresdiscussed herein may be included and/or implemented.

FIG. 4 is a flowchart illustrating an example method for processingmultiple types of activity data from a variety of device types accordingto one or more aspects described herein.

FIGS. 5A-5I illustrate example interfaces a device setup andconfiguration according to one or more aspects described herein.

FIGS. 6A and 6B illustrate example interfaces conveying a batterycharging status according to one or more aspects described herein.

FIG. 7 illustrates an example configuration interface through which auser may define or redefine his or her goal according to one or moreaspects described herein.

FIGS. 8A and 8B illustrate example welcome interfaces according to oneor more aspects described herein.

FIGS. 9A and 9B illustrate example interfaces that may be generated anddisplayed depending on the type of activity data that is to be viewedaccording to one or more aspects described herein.

FIGS. 10A-10G illustrate example activity tracking and monitoringinterfaces that may be used to track multiple types of activities andactivities recorded using multiple types of monitoring devices accordingto one or more aspects described herein.

FIGS. 11A, 11B and 11D illustrate example interfaces providing a graphof activity performed for a period of time such as a goal time periodaccording to one or more aspects described herein.

FIG. 11C illustrate an example interface identifying a best day or timeperiod for a user according to one or more aspects described herein.

FIG. 12 illustrates an interface in which a user's activity over a timeperiod may be replayed according to one or more aspects describedherein.

FIGS. 13A, 13B, 13C and 13D illustrate example summary interfacesdisplaying a user's activity levels over a week, month and year,respectively, according to one or more aspects described herein.

FIGS. 14A-14D illustrate example user profile pages according to one ormore aspects described herein.

FIG. 15 illustrates an example device setting interface according to oneor more aspects described herein.

FIGS. 16A and 16B illustrate example notifications that may be displayedto a user through an on-line activity tracking site according to one ormore aspects described herein.

FIGS. 17A-17D illustrate example interface for sharing activity dataaccording to one or more aspects described herein.

DETAILED DESCRIPTION

In the following description of various example embodiments, referenceis made to the accompanying drawings, which form a part hereof, and inwhich are shown by way of illustration various example devices, systems,and environments in which aspects may be practiced. It is to beunderstood that other specific arrangements of parts, example devices,systems, and environments may be utilized and structural and functionalmodifications may be made without departing from the scope of thepresent disclosure.

Overview

FIG. 1 illustrates a general network and system environment in which oneor more aspects described herein may be used and operate. For example,environment 100 may include multiple devices connected via various typesof networks, connections and protocols including the Internet,short-range and long-range wireless communications, wiredcommunications, cellular communications, BLUETOOTH (e.g., Low-Energy),ZIGBEE, RFID, Wi-Fi, WLAN, USB, FireWire and the like and/orcombinations thereof. For example, activity monitoring devices 103 a and103 b may be connected to computing devices 105 a and 105 b,respectively, through short-range connections including wired andwireless connections. Activity monitoring device 103 c, on the otherhand, may be connected to a remote activity monitoring and trackingsystem 107 via long-range wireless or wired communications includingWi-Fi, cellular communications, TCP/IP, Ethernet and the like and/orcombinations thereof.

Activity monitoring devices 103 a, 103 b and 103 c may include any typeof activity monitoring system including smartphones, dedicated activitymonitoring devices, sensors and the like and/or combinations thereof.Examples of activity monitoring devices are described in: U.S.application Ser. No. 13/287,047, entitled “Wearable Device HavingAthletic Functionality,” filed Nov. 1, 2011; U.S. patent applicationSer. No. 12/767,288 entitled “Athletic Watch,” filed Apr. 26, 2010; U.S.patent application Ser. No. 12/767,447 entitled “GPS Features AndFunctionality In An Athletic Watch System,” filed Apr. 26, 2010; U.S.patent application Ser. No. 12/767,425 entitled “Athletic Watch,” filedApr. 26, 2010; U.S. application Ser. No. 12/767,308, entitled “AthleticWatch,” filed Apr. 26, 2010; and U.S. application Ser. No. 13/343,587,entitled “Athletic Watch,” filed Jan. 4, 2012, the contents of which arehereby incorporated by reference in their entirety.

Activity monitoring devices 103 a, 103 b, 103 c may include differentsensors (e.g., heart rate monitor, accelerometer, global positioningsystem, cellular triangulation system, shock sensors, temperaturegauges, gyroscopes, light sensors, etc.), may use differentcommunication or data recording protocols, have different calibrationsand/or be configured to detect different types of activity and movement.For example, device 103 a may be configured to detect a number of stepsand a corresponding pace based thereon while device 103 b may beconfigured to detect heart rate and hip movement (e.g., for basketballor other types of sports). Accordingly, the data recorded by devices 103a and 103 b might not be immediately compatible or comparable (e.g., useof differing data recordation protocols). A user may, for instance, haveto view metrics and the recorded data using different applications,services or systems so that the information is appropriately processedand visualized or otherwise conveyed. Even between devices havingsimilar components (e.g., devices 103 a and 103 c), the devices may havedifferent sensitivities or calibrations and thus, the resulting data maystill offer inaccurate comparisons of performance.

To facilitate comparisons and to streamline tracking of overall physicalactivity, activity data may be processed using a multi-activity systemand platform such as system 107. System 107 may host an activitymonitoring and tracking site and community through which users may tracktheir own activity progress as well as connect with other users to shareand/or compare activity levels, compete, engage in joint activities,communicate and the like. As described herein, communication of activitydata between monitoring devices 103 a and 103 b may be facilitatedthrough computing devices 105 a and 105 b, respectively. Activitymonitoring device 103 a may further communicate data with device 105 c.However, use of computing devices 105 a, 105 b, and 105 c might not benecessary, if, for instance, devices 103 a and 103 b includecommunication means (e.g., Internet access or wide-area network access)for interfacing with system 107. In some examples, devices 105 a, 105 band 105 c may also provide intermediate processing of activity data andinclude one or more of a multi-activity system and platform's functionsand/or capabilities.

System 107 may be configured to provide a single source through which auser may view activity data for a variety of activities and types ofactivities performed. Rather than having to view basketball activitydata, for example, through a first site or system and running datathrough another site or system, the user may view the information inaggregate through a single platform or system. Additionally, datarecorded using different monitoring devices or types of activitymonitoring devices such as devices 103 a, 103 b and 103 c may also beaggregated and viewed together. System 107 may also providevisualizations and data processing that allows more granular control ofthe recorded data and activities. For example, system 107 may providethe user with the ability to view sets of activity data based on themonitoring device used, type of activity monitoring device, type ofactivity performed, time period, and/or activity session. Moreover, theaggregation of physical activity data by system 107 may allow a user tomeasure, view and evaluate his or her overall physical activity levels.For example, various physical activity data (e.g., metrics) may be usedto determine a virtual activity metric, such as activity points, toprovide a basis of comparison between different activities and activitysessions. Additionally, a user may define goals that may be achievedthrough performing multiple types of activities, even if the multipletypes of activities are measured using different metrics or providedifferent types of sensor data, and/or if the user uses differentmonitoring devices or types of monitoring devices such as devices 103 a,103 b and 103 c.

Computing devices 105 a, 105 b and 105 c may be configured to providedata processing similar to that of system 107, without requiring data tobe sent to system 107. For example, computing device 105 a may receivedata from multiple monitoring devices 103 a, 103 b and/or 103 c andprovide comparisons and data tracking similar to system 107.Alternatively or additionally, computing devices 105 a, 105 b and 105 cmay also be used in some arrangements to provide intermediate storage ofdata and to facilitate data communication with system 107. For example,if devices 103 a and 103 b include relatively small memory capacities,computing devices 105 a, 105 b and 105 c may be used to store recordeddata from devices 103 a and 103 b, respectively so that devices 103 aand 103 b may delete previously recorded activity data to make space tostore additional new data. Computing devices 105 a, 105 b and 105 c maycorrespond to other activity monitoring devices, telecommunicationdevices such as cellular phones, satellite phones, Internet telephonydevices, smart phones and the like, portable computing devices includingmusic players, video players, laptop computers and the like and/ordesktop computing systems such as personal computers (PCs).

In one or more arrangements, one or more of devices 105 a, 105 b and 105c may be configured differently than the other devices. In one example,device 105 c may be configured for local synchronization and storage ofactivity data while one or more of devices 105 a and 105 b may beconfigured for pass-through synchronization. Accordingly, activity datamay be synchronized between activity monitoring device 103 a and device105 c such that activity data is stored on device 105 c. The activitydata may then be synchronized to multi-activity system 107 at some pointin the future. When in pass-through synchronization mode, device 105 amay facilitate synchronization between device 103 a and multi-activitysystem 107 without intermediate storage. That is, device 105 a might notsupport synchronization between just device 105 a and activitymonitoring device 103 a. The various synchronization configurations ofdevices 105 a, 105 b and 105 c may depend on the type of synchronizationapplications installed and/or executing thereon.

FIG. 2 illustrates an example computing system that may be included inone or more of the devices described in FIG. 1. For example, computingsystem 201 may be adapted to operate as any one of devices 103 a, 103 b,103 c, 105 a, 105 b and 107. As seen in this figure, the computer 201has a computing unit 203. The computing unit 203 may include aprocessing unit 205 and system memory 207. The processing unit 205 maybe any type of processing device for executing software instructions,but may conventionally be a microprocessor device. The system memory 207may include both a read-only memory (ROM) 209 and a random access memory(RAM) 211. As will be appreciated by those of ordinary skill in the art,both the read-only memory (ROM) 209 and the random access memory (RAM)211 may store software instructions for execution by the processing unit205.

The processing unit 205 and the system memory 207 are connected, eitherdirectly or indirectly, through a bus 213 or alternate communicationstructure to one or more peripheral devices. For example, the processingunit 205 or the system memory 207 may be directly or indirectlyconnected to additional memory storage, such as the hard disk drive 217and the removable optical disk drive 219. Computer 201 may further useor interface with other memory storage mediums such as solid statedrives, removable magnetic disk drives and flash memory cards. Theprocessing unit 205 and the system memory 207 also may be directly orindirectly connected to one or more input devices 221 and one or moreoutput devices 223. The input devices 221 may include, for example, akeyboard, touch screen, a remote control pad, a pointing device (such asa mouse, touchpad, stylus, trackball, or joystick), a scanner, a cameraor a microphone. The output devices 223 may include, for example, amonitor display, television, printer, stereo, or speakers.

Still further, the computing unit 203 may be directly or indirectlyconnected to one or more network interfaces 215 for communicating with anetwork. This type of network interface 215, also sometimes referred toas a network adapter or network interface card (NIC), translates dataand control signals from the computing unit 203 into network messagesaccording to one or more communication protocols, such as theTransmission Control Protocol (TCP), the Internet Protocol (IP), and theUser Datagram Protocol (UDP). Network adapters may be wireless or wiredor combinations thereof. These protocols are well known in the art, andthus will not be discussed here in more detail. An interface 215 mayemploy any suitable connection agent for connecting to a network,including, for example, a wireless transceiver, a power line adapter, amodem, or an Ethernet connection. Connection agents may similarly bewireless or wired or a combination thereof. Accordingly, using interface215, computer 201 may be able to access wide area networks such as theInternet in addition to local area networks. In one or morearrangements, a user may browse websites or other network devicesthrough a local or wide area network using interface 215. Data such asphysical activity may be transmitted to or received from local or remotenetwork sources (e.g., devices 103 a, 103 b, 103 c, 105 a and 105 b ofFIG. 1).

Other peripheral devices may be included with or otherwise connected toa computer 201 of the type illustrated in FIG. 1, as is well known inthe art. In some cases, a peripheral device may be permanently orsemi-permanently connected to the computing unit 203. For example, withmany computers, the computing unit 203, the hard disk drive 217, theremovable optical disk drive 219 and a display are semi-permanentlyencased in a single housing. Still other peripheral devices may beremovably connected to the computer 201, however. The computer 201 mayinclude, for example, one or more communication ports through which aperipheral device can be connected to the computing unit 203 (eitherdirectly or indirectly through the bus 213). These communication portsmay thus include a parallel bus port or a serial bus port, such as aserial bus port using the Universal Serial Bus (USB) standard or theIEEE 1394 High Speed Serial Bus standard (e.g., a Firewire port).Alternately or additionally, the computer 201 may include a wirelessdata “port,” such as a Bluetooth interface, a Wi-Fi interface, aninfrared data port, or the like.

It should be appreciated that a computing device employed according tovarious examples of the invention may include more components than thecomputer 201 illustrated in FIG. 2, fewer components than the computer201, or a different combination of components than the computer 201.Some implementations, for example, may employ one or more computingdevices that are intended to have a very specific functionality, such asa digital music player, an activity monitoring device or servercomputer. These computing devices may thus omit unnecessary peripherals,such as the network interface 215, removable optical disk drive 219,printers, scanners, external hard drives, etc. Some implementations mayalternately or additionally employ computing devices that are intendedto be capable of a wide variety of functions, such as a desktop orlaptop personal computer. These computing devices may have anycombination of peripheral devices or additional components as desired.

FIG. 3 illustrates another example computing device which may be appliedto an activity monitoring device such as devices 103 a, 103 b and 103 cof FIG. 1. For example, activity detection and tracking device 300 mayinclude a variety of components including a main controller or hostprocessor 301 configured to execute instructions and control othercomponents of the device 300 in accordance with the instructions. Thedevice 300 may further include memory for storage of data andinstructions including volatile and non-volatile memory such as randomaccess memory (RAM) 303, read-only memory (ROM) 305 and storage 307.Additionally, the device 300 may include a charging component 309 forcharging one or more batteries (not shown) powering the device 300. Thedevice 300 may further include various input and output adapters andother components including an ambient light sensor 311, a displayadapter 313, an accelerometer 315 and input adapter 317. Ambient lightsensor 311 may be used to determine a level of brightness for one ormore displays for viewability. Light sensor 311 may also be used todetermine a general time of day. Input adapter 317 may be configured toreceive and process various types of input including button presses,touch input, scroll wheel input and the like, depending on the types ofinput devices included in the device 300. Accelerometer 315 may beconfigured for detecting movement of the wearable device and the userwhen the device is worn. In some examples, accelerometer 315 may be aone-axis, three-axis or six-axis accelerometer. Other sensors includingheart-rate sensors, temperature sensors, humidity sensors, compass,gyroscopic sensor and the like may also be included in the device 300.

Communication by the device 300 may be performed through wired andwireless connection means. In one example, device 300 may include aradio component 319 configured to communicate with other deviceswirelessly through radio frequency transmissions. The radio component319 may correspond to a BLUETOOTH transceiver, an RFID device, a Wi-LANtransceiver, cellular transceiver and the like and/or combinationsthereof, and/or may include a dedicated processor. Display adapter 313may be configured to control one or more displays of the device inconveying various activity information, interaction information, alerts,notifications and the like. In one example, display adapter 313 may beconfigured to control a first display independently from controlling asecond display of the device 300. The wearable device may furtherinclude location determination components such as global positioningsystem (GPS) component 321. Location determination may also be performedusing other devices including a cellular transceiver (e.g., based oncellular triangulation). Components described herein may be combinedinto a single device or may be distributed over multiple components.Moreover, additional or alternative components may be used to provideadditional or alternative functionalities.

A multi-activity platform and system such as system 107 may beconfigured to receive physical activity data for multiple differenttypes of activities and multiple activity sessions from a variety ofdifferent monitoring/detection devices and types of monitoring/detectiondevices. The various functionalities provided by the system may include:activity data tracking and processing, facilitating activity challenges,interfacing with legacy activity tracking systems, generating communityinformation including activity statistics for an entire community,device configuration, setup and synchronization, tracking and processinggoals, user registration, interfacing with other communities or socialnetworks to obtain or provide relevant information, user profile andsite management and the like.

While the multi-activity platform and system 107 is described as beingseparate from devices 103 a, 103 b, 103 c, 105 a, 105 b and 105 c, allor a portion of the multi-activity platform may be implemented indevices 103 a, 103 b, 103 c, 105 a, 105 b and 105 c. For example, themulti-activity platform may include an application protocol interfaceconfigured to facilitate data communication and interactivity betweendifferent activity monitoring devices, tracking services or systems,activity monitoring applications and the like. As such, regardless ofthe configuration or type of the activity monitoring device (e.g., typesof sensors included or type of activity to be tracked), tracking serviceor system or applications executed thereon, data may be communicated andfunctions may be invoked using a shared framework.

FIG. 4 illustrates an example process through which a multi-activityplatform and system may process activity data from multiple devices andfor multiple activities. In step 400, the system may receive a requestto post data to the system. The request may be received from an activitydetection and monitoring device such as devices 103 a, 103 b and 103 c(FIG. 1) or from an intermediary device such as computing devices 105 aand 105 b (FIG. 1). In step 405, the system may receive the physicalactivity data from the requesting device. The physical activity data maybe transmitted according to various protocols and, in at least oneexample, may be transferred using an API provided by the system, asdiscussed in further detail herein. In step 410, the system maydetermine a device type of an activity detection and monitoring deviceresponsible for recording the physical activity data. Device types maybe indicative of device capabilities, a type of activity for which thedevice type is configured for use, device components, data accuracy,data recording parameters (e.g., how frequently data is collected), andthe like and/or combinations thereof. The device type may be determinedbased on various parameters specified in the request (e.g., a devicetype parameter in a data posting function of the API) or based on ananalysis of the physical activity data received. For example, the systemmay determine if the physical activity data received includesaccelerometer data, heart rate data, GPS data and the like. Based onpredefined rules, the system may then determine whether the types ofdata in the physical activity data correspond to a first device type ora second device type. In another example, the system may receive adevice identifier such as a user specified name, a brand, a productname, a serial number and the like and determine the device type basedthereon. In a particular example, the device identifier may bepre-associated or registered with the device type at a time of deviceregistration. Various other manners of determining device type may alsobe used as needed or desired.

In step 415, the system may further determine a type of activityassociated with the received physical activity data. In one example,this determination may be made based on the type of device from whichthe data was received. For instance, a first type of device may beconfigured for a first activity type such as basketball while anothertype of device may be configured for a second activity type such asrunning or walking. In another example, the activity type determinationmay be determined based on a data parameter received by the system. Theparameter may be user-specified by a user tagging the activity data withthe type of activity performed or may be tagged by one or more devicesbased on activity type recognition algorithms and methodologies. In oneexample, a device such as the activity detection and monitoring devicemay compare the pattern of physical activity data to previous sets ofphysical activity data and determine similarities. Upon determining thatthe pattern of physical activity is of a predefined threshold match witha previous set of physical activity data (of a known activity type), thedevice may determine that the recently recorded physical activitycorresponds to the same activity type. Various other functions,algorithms and methods may be used for determining activity type.

In step 420, the system may be optionally configured to generateactivity metrics for the physical activity data received. Metrics mayinclude time, pace, distance, heart rate, body temperature, steps taken,calories burned and the like. In some arrangements, the physicalactivity data may already include metrics generated by the activitydetection and monitoring device or an intermediary computing device.Accordingly, the system may be configured to determine whether metricshave already been generated or included in the received activity dataand if not, generate the metrics. However, if the metrics are alreadygenerated/included, the system might not generate metrics. In otherarrangements, the physical activity data may be raw sensor data that hasnot been processed into metrics. Accordingly, if the latter, the systemmay process the raw sensor data into one or more metrics. For example,for accelerometer data and running activities, foot contact time may beidentified from sensor data according to various known methodologies,and pace, distance and speed may be calculated therefrom. The metricsmay be generated using algorithms and methods selected based on thedevice type and/or the type of athletic activity performed. For example,different device types may have different calibration values while datafor different types of athletic activity may correspond to differenttypes of metrics. Different device types may also have different sensorsand thus require different types of algorithms for processing the sensordata.

In step 425, the system may further normalize the activity metricsdetermined from the activity data. Normalization may be performed tocompensate for discrepancies in data accuracy between different devices,different device types, different activity sessions, different activitytypes and the like. Normalization may be performed using predefinedtables or normalization (e.g., calibration) values for adjusting metricsdetermined for certain types of activities or types of devices. Thus,distance run as determined using a first activity monitoring device maybe multiplied by a factor of 1.05 while distance run as determined usinga second activity monitoring device may be multiplied by a factor of0.998. These normalization or calibration values may be determined basedon empirical analysis in one or more arrangements. In other examples,normalization and calibration values may be determined based onstatistical analyses by asking a user to perform a specified activity(e.g., run 200 feet) and recording and analyzing the resulting data.

In step 440, the system may determine a number of activity points toaward the user based on the received physical activity data. In oneexample, a table may be used to define a number of activity points toaward to a user based on various types of metrics, metric values, devicetypes and activity types. For example, a different number of activitypoints may be defined for different device types, different activitytypes or different combinations of device types and activity types. Themetrics and/or raw activity data may also be stored (see, e.g., step435). In some arrangements, activity characteristics such as altitude,terrain, temperature, and weather (e.g., rain, snow, sun) may also beused in the activity point determination process. In one example, ahigher activity point accumulation rate may be used for activities athigher altitudes and/or harsher weather conditions (e.g., accumulationrate higher for snow than rain than sun). These accumulation rates may,in some arrangements, be user-configurable for each of the activitycharacteristics and/or combinations of activity characteristics.

Once the number of activity points has been determined, the activitypoints may be added to a total number of activity points for aparticular time period in step 445. For example, activity points may beaccumulated to achieve a goal during a goal time period (e.g., 1 hour,12 hours, a day, 2 days, a week, etc.) As such, in step 450, the systemmay determine whether the user has achieved a goal, reached a milestoneor the like based on an amount of activity points accumulated. Forexample, a user may have a 3,000 activity point goal for the day.Accordingly, the system may determine whether the user has achieved3,000 activity points for the day. In another example, a milestone maybe defined as reaching 25,000 lifetime activity points. Accordingly, thesystem may determine whether a total of all lifetime accumulatedactivity points has reached 25,000. As such, different activity pointcounts may be kept for different time periods.

If the user has reached a goal or achieved a milestone, a reward oralert may be provided to the user in step 455. The reward may includevirtual items, services, coupons, tickets, currency, virtual currency,items for an avatar and the like. If a goal has not been achieved or amilestone not reached, the system may indicate an amount of progressstill required (e.g., a number of activity points needed) to reach themilestone or goal in step 460.

In addition to receiving data from devices, the system may also beconfigured to transmit data to devices. For example, synchronization ofdata between the system and one or more monitoring devices may includetransmitting physical activity data recorded by a first monitoringdevice to a second monitoring device and/or downloading historicalactivity data recorded by the first monitoring device back to the firstmonitoring device. In some instances, not all data may be transmittedfrom one monitoring device to another and instead, data may be filteredbased on data compatibility, activity type, user performing the activityand the like. For example, a receiving device may be required to havethe capability to record the same type of data (e.g., have the same typeof sensor) as the data to be synchronized from the transmitting device.In another example, data might only be synchronized if the receivingdevice is configured to track and/or monitor an activity typecorresponding to the data. Various other rules may be used to processsynchronization requests. Activity points may always be synchronized solong as the receiving device has the ability to track activity points.

In some examples, transmission and synchronization of data between twomonitoring devices may be facilitated by the multi-activity platform andsystem. For example, the system may be configured to convert data sentusing a first communication protocol with which a receiving device isincompatible to a second communication protocol with which the receivingdevice is compatible. Additionally or alternatively, the content of thedata may be modified by the system according to formatting requirementsof the receiving device (e.g., character limits, image sizes, numberformats, date formats, etc.) and data storage structures or parametersof the receiving device. In one example, user profile information may beautomatically imported from one device to another device. Various datafields available on the first device might not exist on the seconddevice and thus, the system may filter out data for those fields priorto synchronizing the information to the second device. The system may beconfigured to perform a variety of other data and protocol manipulationfunctions to provide compatibility between two devices.

As discussed, an activity monitoring device such as device 103 a, 103 bor 103 c may initially detect and store activity data and subsequentlysynchronize the data with one or more of a local device/application(e.g., device 105 c) and/or a remote multi-activity system/server (e.g.,system 107). In one arrangement, the multi-activity system/server mayrepresent a destination or preferred storage site due to a largerstorage capacity. Accordingly, data recorded by the activity monitoringdevice and/or synchronized to a local device/application such as device105 c may be ultimately transferred to the multi-activity system/serverfor long-term storage so as not to require and/or occupy large datastorage capacities in the monitoring device and/or the local device. Thelocal device may be a mobile communication device such as a smart phone,a portable media device, tablet computer, netbook computer, or laptopcomputer and/or a stationary device such as a desktop computer.

In some arrangements, an intermediary device such as device 105 a mayexecute a synchronization application configured to synchronize databetween the activity monitoring device and the multi-activitysystem/server. Such an intermediary computing device and synchronizationapplication might not be configured to synchronize data between theintermediary device and the activity monitoring device. Instead, thesynchronization application might only synchronize data between theactivity monitoring device and the multi-activity system/server and onlyprovide such synchronization functionality when a connection to themulti-activity system/server is available. In another example orarrangement, a local application/device may synchronize activity datafrom the activity monitoring device independently of synchronizing thedata with the multi-activity system/server. Once a network connection isavailable with the multi-activity system/server or when the user electsto synchronize with the multi-activity system/server, the data may besubsequently synchronized to the multi-activity system/server from thelocal device/application.

Other synchronization processes may also be used. For example, a localdevice/application may synchronize data through the intermediaryapplication/device. In yet other examples, the activity monitoringdevice may be configured to communicate directly with the multi-activitysystem/server (e.g., without first communicating with the localdevice/application or the intermediary application/device) andsynchronize data therewith. As well, the one or more intermediarydevices, with or without any local device(s), may synchronize among anycombination thereof, e.g., depending on connectivity, the desirabilityto keep such combination(s) of devices in synchrony or otherwise. Theactivity monitoring device may or may not be synchronized together withany such combinations of intermediary and/or local device(s). Themulti-activity system/server may or may not be synchronized togetherwith any such combinations of intermediary and/or local device(s) and/oractivity monitoring device.

In order to reduce the amount of overlap in data transmitted andsynchronized, various parameters/settings may be defined to track thedata that has been synchronized to the multi-activity system/server andto a local device/application. In one example, the activity monitoringdevice may store two parameters: a local read offset (LRO) and a localread time stamp (LRTS). The local read offset (e.g., memory locationidentifier) may indicate the offset in the activity monitoring devicestorage (e.g., flash memory) at which the local application/deviceshould begin reading activity data from the monitoring device whensynchronizing. For example, this memory location or offset may specify alocation where a first unread activity data record is stored. In somearrangements, the LRO may represent a synchronization offset for thelocal application/device to which data is synchronized (versus themulti-activity system/server to which data might also be synchronized).The local read time stamp indicates the time stamp of the last sampleread by the local application from the activity monitoring devicestorage. The time stamp may correspond to a time at which the sample(e.g., activity data) was recorded by the monitoring device. Theseparameters are set when (e.g., during or after) the localdevice/application synchronizes with the activity monitoring device. Forexample, the activity monitoring device may set and/or store the localread offset based on the memory location of the activity monitoringdevice storage last read by the local device. In particular, the localread offset may correspond to the offset of the last memory locationread by the local device incremented by one position or memory location(e.g., the first new activity data memory location). As such, the LROand LRTS may help the activity monitoring device, localapplication/device and/or the MSP track the data that has been readand/or the data that has not been read, so that read data is notre-transmitted needlessly to the local application/device duringsynchronization.

Additionally, the multi-activity service/system may define a lastsynchronization offset (LSO) and a last synchronization time stamp(LSTS). The LSO may refer to the offset (e.g., a memory locationidentifier) in the activity monitoring device's storage memory at whichreading and synchronization of data to the multi-activity service/systemshould begin. The LSO may be different than the LRO if the localsynchronization device has read more or less data than the amount ofdata that has been synchronized to the multi-activity service/system. Insome examples, the LRO/LRTS may be updated independently of the LSO/LSTSand vice versa. That is, one set of parameters may be updated withoutupdating the other. On the other hand, if the same data that has beensynchronized to the multi-activity service/system has also been read bythe local device/application, the LSO and the LRO may be the same.

The local device may update (or cause the activity monitoring device toupdate) the LRO and LRTS upon synchronizing data with the monitoringdevice. Moreover, the local device may update the LSO and LSTS, or causethe LSO and LSTS to be updated upon synchronizing data stored in thelocal device to the multi-activity service/system. In some examples,when the intermediary device/application conducts synchronizationbetween the monitoring device/application and the multi-activitysystem/service, only the LSO and LSTS may be updated since theintermediary device does not, itself, store and synchronize any data. Insuch an event, the LRO/LRTS may also be updated to indicate to the localdevice that further data has been already been synchronized to themulti-activity service/system and that the local device does not need tofurther synchronize that data to itself. In one example, theintermediary device/application may initially request the LSO and LSTSfrom the multi-activity service/system and use the LSO and LSTS todetermine a start point in the activity monitoring device's memory forreading data and synchronizing the data with the multi-activityservice/system. In some arrangements, the LRO/LRTS might only be updatedif the LSO/LSTS has been updated to a point beyond the LRO/LRTS (e.g.,in a data storage progression). Using the above process, themulti-activity service/system may avoid receiving data (e.g., from thelocal device) that has already been synchronized to the multi-activityservice/system in the past (e.g., directly from the monitoring device orthrough the intermediary device).

Additionally or alternatively, data of the monitoring device alreadysynchronized to the multi-activity system/service may be deleted fromthe monitoring device. In another example, the data may be deleted ifthe multi-activity system/service has not been synchronized with thatdata; in such case of deleted data, a notification or indicator may beprovided to the activity monitoring device, a local device, anintermediary device and/or the multi-activity system/server indicatingthat synchronization is to be performed with the local device storingthe data that has yet to be synchronized with the multi-activitysystem/service

However, data only synchronized to a local device, and not themulti-activity system/service, might not be deleted. Examples ofcircumstances in which data might not be deleted include, e.g., tomaintain redundancy as to the synched data (such as until a selectedtime has elapsed or a selected event occurred, such as synchronizationto a predetermined device or number of devices, or to the multi-activitysystem/service), or in the event the user wishes to later synchronizethe data through the intermediary device/application instead of usingthe local device, and/or in the case the user wishes to synchronizeadditional local devices from the monitoring device. In other examples,the data may be deleted if the multi-activity system/service has notbeen synchronized with that data. Instead, a notification or indicatormay be provided to the activity monitoring device, a local device, anintermediary device and/or the multi-activity system/server indicatingthat synchronization is to be performed with the local device storingthe data that has yet to be synchronized with the multi-activitysystem/service. Data synchronized to the multi-activity system/servicemight not be deleted from the activity monitoring device in someinstances if, for example, the data has not yet been synchronized to thecurrently proximate local device/application. The deletion of data fromthe activity monitoring device may be configurable by the user.Alternatively or additionally, data may be deleted once synchronized tothe multi-activity system/service and/or to any other device in theevent that the amount of space remaining on the activity monitoringdevice decreases below a specified threshold.

According to other aspects, data from an activity monitoring device maybe synchronized to multiple local devices. In such a configuration, eachlocal device may set to a different set of LRO and LRTS markers uniqueto that local device.

In yet other arrangements, if a local device determines that the user isattempting to synchronize a threshold amount of data from the monitoringdevice, the local device may provide a message/recommendation to theuser to use the intermediary device/application instead. Thisrecommendation may be provided in circumstances where the intermediarydevice/application is configured to read data off of the monitoringdevice at a faster rate than the local device (e.g., USB vs. BLUETOOTH).

In yet other examples or arrangements, the above described offsets andsynchronization processes may be activity type or device type specific.For example, a running LRO, LRTS, LSO and LSTS may be definedspecifically for a buffer or storage area configured to store runningdata while a basketball LRO, LRTS, LSO and LSTS may be defined for adifferent buffer or storage area configured to stored basketball data.Similar offsets and/or storage areas may be defined for different datarecording device types. Accordingly, applications that are configured tosynchronize one type of activity or data from one type of device but notanother may modify the offsets/parameters for only one of the storageareas/activity types/device types while not affecting the others. Such aconfiguration may add flexibility to synchronization capabilities.

By using the above noted offsets and timestamps, the amount of data thatmay be synchronized is optimized such that new or unsynchronized data isto be synchronized to a recipient device.

Monitoring Device Setup/Configuration

A multi-activity platform and system may further allow devices, systemsand applications to setup and configure various types of monitoringdevices. In some arrangements, an intermediary computing device such asdevice 105 a or 105 b may serve as a multi-activity system that isconfigured to communicate with and interact with a various monitoringdevices and device types that may be configured to detect and monitor avariety of types of activity. For example, intermediary application orcomputing device may be used to register users or devices with amulti-activity service or system such as an on-line community orservice. In a particular example, the intermediary application orcomputing device may be configured to register multiple differentdevices and device types.

FIGS. 5A-5E illustrate example interfaces for a device setup andconfiguration application that may execute on a user's local computingdevice to which an activity monitoring device may be connected. In oneexample, the application may be stored in the activity monitoring deviceand downloaded and installed to a user's device upon connection.Alternatively or additionally, the activity monitoring device may storea location identifier such as a URI with an instruction for thecomputing device to retrieve and install the data located at the URI. Instill another example, as illustrated in FIG. 5A, the activitymonitoring device may specify a URI where the device may be introducedand an option may be provided to download a corresponding applicationfor configuring the device. The local computing device may thenautomatically navigate to the URI upon connection of the activitymonitoring device.

FIGS. 5B-5D illustrate example device configuration interfaces that maybe provided upon downloading the device configuration application. FIG.5C, for example, allows the user to specify user characteristics such asheight and weight to help better calibrate the device as well asidentify a wrist on which the device will be worn. Other types of usercharacteristics may be defined and provided as configuration options asdesired or needed. For example, the device may be worn on other parts ofthe user's body. Age may also be added as a user characteristic forcalibration purposes. In FIG. 5D, the user may be presented with aninterface for setting an activity goal. The user may select any ofmultiple predefined levels or define his or her own goal manually (notshown). The goal may then be stored to the monitoring device for goaltracking and progress monitoring.

FIG. 5E illustrates an example interface through which a user may createor login to an on-line activity tracking and monitoring service. Theuser may be provided the option of registering a username specific tothe service or using a login for an external site (e.g., an externalsocial community network) as a login for the activity tracking andmonitoring service. The various configuration and login information maybe communicated to the monitoring device through the shared API asdiscussed herein. Additionally, a status of the device may be retrievedusing the shared API as well. Other monitoring devices and device typesmay similarly be configured using the shared API. For example, theconfiguration and setup application may be configured to interact withmultiple types of monitoring devices.

FIGS. 5F-5I illustrate further example application interfaces throughwhich a user may configure an activity monitoring device. In FIG. 5F,for example, a user may specify his or her birthdate, gender, height andweight. In FIG. 5G, the user may further indicate how the device shouldobtain a time of day. The user may manually enter the time of day or mayobtain time and date information from one or more other systems such asthe computing device through which the device is being configured, acellular system, a satellite and the like. The user may also indicatewhether 24-hour or 12-hour time should be used. FIG. 5H illustrates aninterface through which a user may select metrics that are to bedisplayed on the device. For example, a user may select to displaycalories, but not steps. Other settings may similarly be defined. FIG.5I illustrates an interface through which a user may configure displayoptions such as whether to use a goal indicator light and/or to includegoal celebrations. Various other configuration options may be added orremoved as desired or needed.

The configuration application may be configured to interact andconfigure multiple different types of devices. Accordingly, theconfiguration interfaces may differ in content and/or appearancedepending on the type of device connected. In one example, theapplication may identify the type of device connected and automaticallyexecute the appropriate APIs and display the corresponding interfacesfor the identified type of device. The different interfaces may offerdifferent configuration options such as different displayable metrics,color configurations (e.g., if the device support color displays),display configurations (e.g., different options depending on a number ofdisplays included in the device) and the like and/or combinationsthereof.

FIG. 6A illustrates an example interface conveying a battery chargingstatus of the device. In some examples, the device might not be useablefor a first time until the device has reached a specific level of charge(e.g., 50%, 65%, 70%, 80%, 90%, 95%, 100%, etc.).

When the device has reached the requisite level of charge, a displaysuch as the interface of FIG. 6B may be provided.

FIG. 7 illustrates another example configuration interface through whicha user may define or redefine his or her goal. The user may change agoal for the current time period or for any other time period asdesired. Once the user has confirmed a goal, the goal information may besynchronized to the user's device using the various shared APIsdescribed herein.

Multi-Activity Community

A multi-activity system or service may include an on-line community orsite that allows a user to review activity information for not only hisor her activities but for other activities. The review may include avariety of information types including audio, video, text and the like.For example, motivational messages (e.g., user generated or systemgenerated) may be provided to users through audio messages. Users mayalso record audio notes to be stored in association with one or moreactivity sessions, goal time periods or the like.

The on-line community or site may provide a user with different initialinterfaces depending on the user's status. For example, if the user isnew to the community, a first interface may be displayed. On the otherhand, if the user is a returning user, a second interface may be presentto the user upon login.

FIG. 8A illustrates an example welcome interface that may be displayedfor a new user on an on-line community or site upon user login. Theinterface may provide options to the user to purchase activitymonitoring devices, or to specify the type of monitoring device or otherequipment that the user already has purchased and/or will be using ifknown. In some arrangements, the registration/configuration applicationmay automatically notify the on-line community of registered devices andthus, the welcome interface for users (regardless of new or returning)may acknowledge the existence of a registered device upon login. Forexample, the list of product recommendations might not include onesalready purchased and/or registered. The interface of FIG. 8A mayfurther provide a link to download a registration/configurationapplication. Again, if the user has already downloaded the application,the interface might not provide the link.

FIG. 8B illustrates an example welcome interface that may be displayedto an existing user of the on-line community/site. Instead ofrecommending products or providing options for downloading deviceapplications, the interface may include options for viewing activitydata. Activity data may be categorized based on type of activity and/ortype of device used to record the activity data. Accordingly, theinterface may provide multiple options for review of activity datadepending on the types of activity in which the user has engaged and/orthe types of devices the user has used to record his or her activity. Asdiscussed herein, a multi-activity platform and system may be used toreceive and differentiate between data of different activity types anddevice types. Accordingly, the on-line site/community may automaticallyrecognize when different activity types and device types are representedin the activity data.

Additionally or alternatively, activity of different activity types orrecorded using different device types may be visualized in differentways (e.g., colors, themes, interfaces, types of graphs, types ofstatistics, etc.). FIGS. 9A and 9B illustrate different interfaces thatmay be generated and displayed depending on the type of activity datathat is to be viewed. FIG. 9A, for example, displays activity datarecorded using a first type of monitoring device in a first type ofvisualization interface. Details of the interface are described infurther detail herein. FIG. 9B illustrates a second type ofvisualization interface for visualizing activity data recorded using asecond type of monitoring device. Types of devices may differ based oncapabilities, calibration, types of sensors used, area on which thedevice is configured to be worn and the like. Accordingly, differentvisualizations and/or interfaces may be provided for different types ofdevices regardless of the type of activity performed (e.g., the types ofactivity recorded using the different types of devices may be the sameor different). In a particular example, a first visualization or set ofvisualizations may be automatically generated upon uploading/receipt fordata from a first type of device and/or a first type of activityperformed while a second visualization or set of visualizations(different from the first visualization or first set of visualizations)may be automatically generated for data from a second type of deviceand/or a second type of activity performed. While the user may requestadditional types of visualizations (e.g., those provided as part of thefirst set of visualizations) for the second type device or second typeof activity, only the second visualization or set of visualizations maybe automatically provided as an initial set available uponupload/receipt of the data.

In other examples, various activity metrics may be viewed in a sameinterface or display regardless of the device type or activity type. Forexample, users may be able to track progress toward a goal that may beachieved through performance of multiple types of activities andregardless of the type of device that is used to record thoseactivities. Additionally or alternatively, different graphs (e.g., linegraphs, bar graphs, etc.) may be overlaid on the same chart/axes.

FIGS. 10A-10G illustrate example activity tracking and monitoringinterfaces that may be used to track multiple types of activities andactivities recorded using multiple types of monitoring devices. Theinterfaces may also be used to tag additional information about thevarious activities and activity sessions performed and to track progresstoward an activity goal. FIG. 10A, for instance, illustrates aninterface indicating that that user has recorded no activity and made noprogress toward an activity goal. The interface of FIG. 10A may bedisplayed, for example, when a user first registers with the service andhas not performed or synchronized any activity data with the on-linecommunity. The interface may further display information such as anamount of progress toward a milestone. A milestone may differ from agoal defined for a specified goal period. For example, a goal period maybe of a finite amount of time and goal progress may be determined basedon activity performed during that finite amount of time. Goal timeperiods may also be recurring on a regular schedule. Milestones, on theother hand, may refer to achievements reached over a course of a user'slifetime of activity performed (e.g., reaching 50,000 activity points inthe user's lifetime). Milestones may be unique. For example, eachmilestone might only be achieved once. Alternatively, milestones may bedefined for finite time frames including a goal time period. In someexamples, milestones may be defined for any time period different from aspecified goal time period. In still other examples, milestones andachievements may relate to metrics other than a goal metric.Additionally or alternatively, milestones may also be uniquelygenerated/defined for each user based on user characteristics,interests, etc. For example, if a user enjoys running versus playingbasketball, a distance milestone may higher than for a user when enjoysplaying basketball more than running. Milestones may further differ forvarying ages or age groups. Various configurations of milestones andgoals may be used.

The activity tracking interface may further include a section comparinga user's performance against users of the community and/or groups ofusers in the community. For example, in FIG. 10A, the user's weeklyactivity points are compared against the entire community of users aswell as a community sub-group of men of the same age as the user. Theuser may configure (e.g., select and/or define) the sub-groups andnumber of sub-groups to which his or her performance is to be compared.The user may further configure the activity time period to be compared(e.g., daily, weekly, monthly, etc.).

FIG. 10B illustrates an interface that may be displayed when a user hasrecorded and synchronized activity data. As shown, the interfaceindicates that the user has made progress toward a milestone ofaccumulating 10,000 activity points over the user's lifetime. Theinterface may also include an option to view subsequent milestones.Milestones may be consecutive or progressive in nature such that a usermust complete a first milestone before reaching a second milestone.

FIG. 10C illustrates another interface displaying a user's progress madetoward a goal as well as a milestone. Other activity summary informationmay also be provided including whether a streak has been achieved and alength of the streak, a number of goals reached, and various metrics fora selected goal time period. In one example, a section of the interfacemay display detailed metrics and activity information for a selectedgoal time period. Different goal time periods may be displayed asselectable section labels along a side of the display section. Inaddition to identifying the goal time periods (e.g., days, hours, weeks,etc.), the section labels may also display a progress made toward thegoal for those time periods. For example, the section labels mayindicate whether the user completed the goal by that day, whether amoderate amount of progress was made toward the goal (but not completed)or if a low level of progress was made toward the goal. Other indicatorsmay also be included as part of the goal time period section labels. Forexample, if a user reached a milestone during that goal time period,another symbol or indicator may be displayed. In another example, if auser exceeded his or her goal by a specified amount, yet another symbolor indicator may be used as indication. Different colors, indicators,patterns, symbols, characters, transparencies and the like may be usedto differentiate between goal progresses, other achievements, events andthe like.

The activity detail display for a goal period may include a goal meterthat indicates whether the user met his or her goal and if not, anamount of progress made towards the goal. In addition, a graph may bedisplayed to illustrate a breakdown of activity level over the goal timeperiod. Various peaks in activity may also be identified in the graphwith an indicator such as “SPARK.” Peaks may be defined by an activitylevel exceeding a threshold amount of activity, the top number ofactivity levels in the goal time period, and the like. For example, thetop 1, 2, 3, 4, 5, 10 peaks may be indicated in the graph. Variousmetrics may also be displayed in a portion of the detail display such ascalories burned, distance traversed, steps taken and/or time active.Another portion of the display may display a current streak (e.g., acurrent number of consecutive goal time periods in which the goal hasbeen reached) and a number of goals hit in the user's lifetime (or aspecified time period). This portion of the display may display a streaktracker that provides an indication of a number of consecutive goal timeperiods including a current goal time period and a goal progressionstatus for each of those time periods. The interface may also identifythe longest streak the user has achieved. Alternatively or additionally,the system may also provide an indication of a number of streaksachieved. In yet another portion of the interface, the display mayprovide a recommendation for raising or lowering the goal. For example,if a user has exceeded previous goals by a specified amount (e.g., anaverage amount by which the user exceeded one or more previous goals, anaccumulated amount by which the user exceeded the one or more previousgoals, a greater, median or lowest amount by which the user exceeded oneor more previous goals, etc.), the system may recommend that the userincrease a next goal (e.g., by that specified amount or an even greateramount).

FIG. 10D illustrates an example general summary interface that is notspecific to any particular goal time period. The general summaryinterface may provide information regarding a recent predefined timeperiod such as a most recent week, month, year, a time period since alast synchronization with a monitoring device or a particular monitoringdevice and the like. The general summary interface may indicate a numberof achievements reached, an amount of activity points earned since thelast synchronization and/or a number of active days (e.g., a number ofdays in which a threshold level of activity was reached).

FIG. 10E illustrates an achievement celebration, where the achievementcorresponds to exceeding a goal by 40%.

FIG. 10F illustrates an interface through which a user may specify asubjective feeling they had toward or during the activity time period oractivity session. The user may select/specify an emoticon and/or provideuser-specified comments or notes regarding that time period. Thisinformation may then be stored in association with the goal time period,activity session, and/or the user's account. In other examples, activitysessions and activity points may be tagged or otherwise labeled withlocation information and/or time information. Geographic location may betagged using one or more location determination systems such as GPS,cellular triangulation, Wi-Fi location determination based on ISP andthe like. Location determination systems may be internal to orintegrated with the device or may be separate from the device (e.g., amobile communication device such as a smart phone having GPSfunctionality). Time may be determined based on the time of the deviceor times of other devices, servers and systems. Accordingly, activitypoints and activity data in general may be filtered and viewed in agranular fashion based on geographic location and/or time. This taggedor additional information relating to particular activity points oractivity sessions may be stored as metadata in one or more examples.

FIG. 10G illustrates an interface that may be displayed after a user hasentered a user's subjective feeling and notes about the activity timeperiod.

FIGS. 11A and 11B illustrate example interfaces providing a detailedgraph of activity performed for a period of time such as a goal timeperiod. A user may hover over or otherwise interact with portions (e.g.,any portion or specific portions) of the graph to obtain activitymetrics and information specific to the particular point in time or ofthe graph. Indicators may be provided on the graph to indicate variousevents such as a point at which the user hit the goal and a peakactivity level. For example, FIG. 11D illustrates an indicatoridentifying a time period such as an hour in which the user was mostactive. If the goal time period displayed corresponds to a best day, abanner or other indicator may also be displayed in the detailedinterface. A best day or best activity time period may be defined as aday or other time period during which a highest amount of activitypoints was earned, a metric reached an all-time high (e.g., a pace,distance, etc.), a user was active for a greatest amount of time (e.g.,most active hours) and the like. A portion of the interfaces may alsodisplay a comparison of the current time period against other timeperiods.

FIG. 11C illustrates a best day indication interface.

FIG. 12 illustrates an interface in which a user's activity over a timeperiod may be replayed. For example, the graph may be animated such thatthe user's activity is graphed in animation fashion over the goal timeperiod.

In some examples, the interfaces may display activity levels along witha breakdown of types of activities and types of monitoring devices thatcontributed to the accumulated activity. For example, hovering over orotherwise interacting with a graph of activity points may display a listof activity types, activity sessions, device types and the like that areassociated with the activity points accumulated. The list of activitytypes, activity sessions and/or device types may further include anindication of an amount of activity points accumulated for each of thosevarious parameters. The user may also filter data displayed in anactivity point graph by the above noted parameters. For example, thegraph may be filtered such that only activity points accumulated from aparticular type of activity is displayed. In another example, the graphmay be filtered such that only activity points accumulated using aparticular type of monitoring device is displayed in the graph. In yetanother example, the graph may be filtered such that only activitypoints accumulated during a particular activity session are shown. Instill other examples, activity data and activity points may beassociated with specific monitoring devices. Thus, a user may be able todifferentiate between activities performed and activity pointsaccumulated based on the device that was specifically used. Additionallyor alternatively, the activity points corresponding to the differenttypes of activities, different types of monitoring devices and/ordifferent activity sessions may be displayed with different appearancesin the graph. For example, accumulated activity points for a first typeof activity may be displayed in red while activity points accumulatedfor a second type of activity may be displayed in yellow and so on. In aparticular example, the different activity types may be included in thesame bar graph or line graph, but each portion corresponding to adifferent activity type may be displayed with a different appearance.Various other visual configurations may be employed and may be userspecified.

FIGS. 13A, 13B and 13C illustrate example summary interfaces displayinga user's activity levels over a week, month and year, respectively. FIG.13D illustrates another example monthly summary interface. Each of theinterfaces in FIGS. 13A-13D may display the user's activity level ofthose time periods with a further breakdown based on a smaller timeframe. For example, a weekly summary may include daily bar graphs whilea monthly summary may include weekly bar graphs. Interacting with (e.g.,hovering over) one or more of the entries may display more specificactivity information and details including metrics, types of devicesused, activity sessions, types of activities performed and the likeand/or combinations thereof. The interfaces may also display a goalcompletion rate for that summary time period. For example, in the weeklysummary of FIG. 13A, the interface may display a number of daily goalshit and/or a percentage of goals reached.

FIGS. 14A-14D illustrate example profile pages for a user. The user'sprofile page may include a listing of records, recent activity,achievements, milestones, awards and the like. Additionally, the user'sprofile may provide summary information for the user including a devicemost used or device type most used, a type of activity most frequentlyperformed, activity point averages, other average metrics, personalinformation (e.g., name, age, location, birthdate, etc.) and the like.FIG. 14A illustrates a profile interface that may be displayed when theuser has not registered or synchronized any activity data. In somearrangements, the user's profile page may also display devices and/ortypes of devices the user uses for recording activity.

FIG. 15 illustrates an example device setting interface. Each deviceregistered for the user may have a different device setting interface onthe on-line site. The device setting interface may display informationabout settings registered in the device such as a current time and daterecognized by the device, types of data (e.g., metrics) to be displayedon the device, an orientation of the device (e.g., a wrist or otherlocation on which the device is worn) and a language setting. In someexamples, the interface may allow the user to edit or update settings onthe device. The interfaces for the different devices may includedifferent setting parameters and information. For example, an interfacefor a first device may include GPS settings while an interface for asecond device might not include GPS settings if the second device doesnot include a GPS sensor. The device-specific interfaces may alsoinclude activity data and summaries (as described herein) for activitiesdetected using the corresponding device. Accordingly, thesesub-interfaces may allow a user to display activity of the user at amore granular level. In some arrangements, an on-line site or communitymay further identify a type of device or a specific device mostfrequently used by the user to record activity data or a device or typeof device with which a user has recorded a most amount of activity.

FIGS. 16A and 16B illustrates example notifications that may bedisplayed to a user through an on-line activity tracking site.

FIGS. 17A-17D illustrate example interface for sharing activity data. InFIG. 17A, for example, a user's profile may be populated withinformation about other users. For example, a notification or news eventmay be posted to the user's profile to alert the user of the otheruser's recent activity or activity event. For example, the other usermay have recently completed a goal or reached a milestone. Such eventsmay be displayed to the user to act as motivation and to encourage theuser to congratulate the other user. Activity sharing may be configuredon or off. Other sharing parameters may be defined as well. For example,a user may identify users and/or groups to which activity should beshared. In other examples, a user may define times during which sharingis allowed and/or types of events or activities that may be shared. In aparticular example, a user may specify that events or activity dataresulting from a first type of device, a first type of activity or aparticular activity session is to be shared while events and/or activitydata resulting from a second type of device, a second type of activityor another specific activity session is not to be shared. Thus, the useof the multi-activity platform allows a system to provide more granularcontrol in sharing activity information. Activity may be shared throughthe user's profile (e.g., when other user's view the user's profile) oras part of other user's profile, activity feeds and the like. Forexample, activity events and information of a first user may be pushedto a profile or page of another user.

FIGS. 17B-17D illustrate example interfaces for sharing activityinformation and events through external social community and networkingsites. FIG. 17B illustrates an interface including options for sharingon FACEBOOK or TWITTER. FIGS. 17C and 17D illustrate pop-up interfacesthrough which a user may submit a note, specify activity information tobe shared, identify users to which the information is to be shared, andthe like. As with configuration information that is and is not to beshared, the user may configure sharing of information through externalsites and systems based on device type, activity type, activity sessionand the like as well. In one example, the user may configure sharing ofinformation through external sites and systems separately from sharingthrough internal systems or communities.

Multi-Activity Application/Device Interface

Interaction between activity monitoring devices, activity trackingservices and systems, intermediary devices and other computing devicesor systems and/or applications executing thereon may be conducted usinga shared application protocol interface (API). For example, applicationsexecuting on a smart phone may use the API to retrieve data from andtransmit data to activity monitoring devices adopting the API.Similarly, communications between an activity monitoring device and anactivity tracking service or system may be conducted using the API.Communications between dedicated activity monitoring devices may also beconducted using the shared API. The use of such an API allows forinteroperability between devices of different types and activity data ofdifferent types. An example of the protocol is described in furtherdetail below.

Activity Data Tracking and Processing

The API for activity data tracking and processing may include a varietyof functions including activity deletion, activity detail requests forone or more activities, activity listing requests, activity summaryretrieval, posting and deleting tags, requesting activity type-specificinformation, requesting activity data based on date ranges and the like.The API may be used for monitoring devices and other devices to interactwith a multi-activity system as well as for the multi-activity system orother computing devices to retrieve information from and transmitinformation to the monitoring devices.

Activity Delete: This service/interface may be used to delete anactivity (e.g., an activity session having a particular activity sessionidentifier). Once deleted, a user will no longer be able to view thisactivity, and it might no longer be used for any calculations,aggregations or challenges. For example, a number of activity pointsawarded for the activity may be deducted from a total activity pointamount upon deletion. Alternatively or additionally, the activity deletefunction may be activity type-specific. Accordingly, an activity deletecommand may cause all activity data for a particular type of activity tobe deleted.

Activity Detail: Devices may also be able to retrieve detail on a singleactivity or activity session or by activity-type. This service returnsall the information related to a specific activity using the activity IDas parameter or activity type and/or a list of activity sessions of anactivity type using type specifications. Details may include raw sensordata, metrics, location information, participating individuals and thelike.

Activity Detail for the Last Activity: This service returns informationrelated to the last activity session. Accordingly, instead of having tobe aware of the ID of the last activity session, the system may providea function call that is particular to the most recent activity. The usermay also specify an activity type, thus allowing a device to select alast activity session for a particular activity type. Similarly, othertypes of parameters may be used to further or differently distinguishbetween last activity sessions.

Activity List: Return a list of the user's activities. This service isuseful for any application wishing to obtain a list of activities bydate, time or index. For example, a device may request all activitiesperformed between two particular dates or times. The list may further befiltered based on other parameters including activity types, devicetype, device ID, activity characteristics (e.g., above or below athreshold pace, a particular weather condition, a particular terrain orlocation, activity equipment used etc.) and the like. Retrieval usingindices may refer to specifying an activity ID range and retrieving allactivities within that ID range.

Activity Summary for the Specified Month: This function allows a deviceto retrieve a user's activity summary for a specified month. Theactivity summary may include statistics regarding a number of goals met,an average number of activity points earned (or other activity metric),identification of streaks of goal completion and the like, as isdescribed in further detail below.

Activity Summary for the Specified Week: Get a user's activity summaryfor a week.

Activity Summary for the Specified Year: Get a user's activity summaryfor a specified year.

Activity Update: This service returns all the information related to aspecific activity using the activity Id as a parameter. In someexamples, this function may include a date or time parameter specifyinga last time when information relating to the specific activity wasretrieved. The device or system from which this information is requestedmay then transmit all information that is new as of the specified dateor time.

Basketball Activity Detail: As described, activity data requests may beactivity type specific. Accordingly, an activity type specific functionmay be provided to retrieve details on a single basketball activitysession. This service returns all the information related to a specificactivity using the activity Id as parameter.

Basketball Activity List: Return a list of the user's basketballactivities.

Customized Tags: Adds user customized tags for specified user. Forexample, a user may be allowed to define customized characteristic tagsfor activity sessions. Tags may include, weather, equipment, terrain,food eaten prior to the activity session, user-specified notes and thelike.

Daily Activity Point Summary Service: Gets a user's daily activity pointhistory over an interval. For example, a time period such as 9 AM-12 PMor 9 AM-6 PM may be specified and data for that time period may beretrieved for each day. Alternatively or additionally, differentactivity point periods may be defined for retrieval such as a weeklyactivity point history or an hourly activity point history.

Delete Tags: Deletes the user tags for a specified activity.

Extended Metrics: Adds user extended metrics for specified activity orgets a list of the extended metrics associated with the activity Id ordeletes a list of the extended metrics. Extended metrics may refer tometrics that are not automatically synchronized. In other examples,extended metrics may refer to any metrics that are userentered/specified (e.g., not automatically detected or generated by anactivity tracking device or monitoring system).

Get Datastreams for Start and End Time: Get datastreams for a start timeand an end time. This service returns all the datastream informationrelated to the user between the designated start and end timeparameters. For example, the datastream may include activity data andinformation as well as other actions taken by the user such as updatingof a profile, adding a friend, setting a goal and the like. Accordingly,this function allows for retrieval of data beyond recorded athleticactivity data and may include all actions taken with a particular deviceto which the command is being sent.

Get Tags: Gets the user tags for specified activity session. In oneexample, this function may enable a device to retrieve the values forvarious tags within activity data. In some arrangements, various sets oftags may be defined for different activity types (or for differentdevice types). Accordingly, upon determining the tags that areassociated with an activity type or device type, the system may retrieveor extract values for those tags from the activity data

Get User Events: Return list of user events to be displayed. User eventsmay refer to actions taken by the user or achievements/goals reached.

Post Tags: Adds the user tags for specified activity. Accordingly, auser may tag activity data stored on one device via a second, physicallyseparate (and potentially remotely located) device.

Post Tags By Date Range: Tags all the activity sessions in the specifieddate range with one or more specified tags. Tags may relate to a user'ssubject feeling, weather conditions, terrain, equipment used and thelike. In some examples, the function may also be configured toautomatically calculate the values for tags associated with the activitytype and store those values in association with the tags for theactivity session or activity data.

Running Activity Detail: This service returns all the informationrelated to a running activity using the activity ID as parameter.

Running: My Activities: Returns a list of sport activities for runningand their aggregations.

Running: My Activities v1.0: Returns activity report, activity historydetails and lifetime details for a user for running activities.

Running: My Activity: Returns a sport activity by activity id for auser.

Training Activity Detail: Get detail on a single activity. This servicereturns all the information related to a specific activity using theactivity Id as parameter.

Training Activity List: Return a list of the user's activities summaryfor a training-type activity.

Challenges

Challenges may be issued and conducted between two users using twodifferent devices and device types. The following provides a list ofAPIs that may be used to create, track and complete a challenge.

Accept Challenge: Accept a challenge.

Accept or Deny Challenge: Accept or Deny challenge will be a user'sresponse once they have been invited to a challenge.

Add Challenge: Add a challenge with the supplied information such as anobjective, a duration, participants, whether the challenge is public orprivate, location, name of the challenge, start time and the like. Insome instances, the add challenge service allows a user to specify apredefined challenge type such as Create Daily Goal, Challenge of theWeek, Head to Head, Group Fuel Goal, Group Workout, Drill BasedChallenge and Team Up, as described in further detail herein. Privacylevels may also be set. For example, the following table describesexample privacy levels.

Id Description 0 Private. You can only join if invited by the challengecreator. Only the participants can view the results of the challenge. 1Participants and friends of creator can view. Does not appear onsearches. (Note: As the concept of friends does not exist right now onMSP, 0 and 1 are the same.) 2 Public. Appears on searches. Anybody canview the challenge details and leader board, but not join. 3 Public.Appears on searches. Anybody can join, view the challenge details andleader board.

Create or Update Challenge: Using this service, different types ofchallenges can be created/updated. The business rules and requiredparameters depend on the type of the challenge being created. Thechallenge types are: Create Daily Goal, Challenge of the Week, Head toHead, Group Fuel Goal, Group Workout, Drill Based Challenge and Team Up.

Challenge of the Week: Creates a challenge of a type that can only becreated once a week. The challenge of the week may include variousrewards that are specific to this type of challenge.

Create or Update Daily Goal: This service is used to create/update thedaily goal for a specified date. If the date supplied is today, thedaily goal for today will be changed/updated. If the date supplied isany date in the future, the future daily goal value will be changed. Anerror will be returned if the date supplied is prior to today.

Drill Based Challenge: Challenges can be created based on a drill. Thisform of the service will look up the details of an existing drill andcreate a challenge matching the parameters of the drill. Drills mayrefer to a predefined sequence of physical movements at specified times.Groups may or may not be supported. The overview of this Head to Headchallenge is of a non-competitive variety. A challenge of this typeindicates that the creator of the challenge invites her/his friends tobeat their challenge. Whether the participants beat the challenge ornot, the result is sent to back to original challenge poster. That is,the participants performance are not compared with one another and is,instead, compared to the objective. Thus, multiple participants may beatthe challenge.

Get Challenge Details: Gets all the details of a challenge and theassociated leaderboard (e.g., a listing of participants and a currentlevel of performance/progress). In some arrangements, this function maycheck whether the logged-in user has permissions to see the requestedchallenge details.

Get Challenge List 1.0: Get a list of the challenges past and present onwhich a specific user has participated either as creator or as member.The list may be ordered by the end date of the challenge with the mostrecent challenge listed first. This service also lists goals, which is atype of challenge (me vs me) where there are no challenge members (otherthan the creator/user) or leaderboard.

Get Daily Goal List: Get a list of daily goals across multiple dates forthe given user.

Group Activity Point Goal: The group activity point goal is a challengetype, which is individual based (but in a team), and non-competitive. Achallenge of this type involves a creator of the challenge invitingher/his friends to join in the challenge and the sum of the activitypoints of all of the members/participants should be larger than apredetermined amount at the end of the challenge. There may be severalbusiness rules for this challenge type. For example:

1) A user can have up to 5 challenges of this type, including createdchallenges and accepted challenges, e.g., if a user has already created5 challenges, the user cannot accept other challenges.

2) Each challenge of this type may hold up to 5 users (excluding thecreator), i.e., the creator of a challenge can specify at the maximum 5friends to send invitations to.

3) Challenges of this type may always be 7 days long.

4) After a challenge ends, velocity can make a call to create a newchallenge with the same parameters.

5) The invitation can be accepted at any time within the 7 days, theamount of fuel earned since the start time will be credited to thechallenge.

6) A challenge is not expected to be changed after it is created.

Other rules, restrictions and the like may be defined and is not limitedto the above example.

Group Workout: The group workout is a challenge type, which isindividual based (but in a team), and non-competitive. A challenge ofthis type is that the creator of the challenge invites her/his friendsor other participants to join in the challenge and each member in thechallenge should do at least the predetermined amount of workout. Theremay be various business rules for this challenge type. For example:

1) A user can have up to 5 (or any other number) challenges of thistype, including created challenges and accepted challenges, e.g., if auser has already created 5 (or other number) challenges, the user mightnot be allowed to accept other challenges.

2) Each challenge of this type can hold up to 5 users (excluding thecreator), i.e., the creator of a challenge can specify at the maximum 5friends to send invitations to.

3) Challenges of this type might always be 7 days long.

4) After a challenge ends, velocity can make a call to create a newchallenge with the same parameters.

5) The invitation can be accepted at any time within the 7 days, thenumber of workout performed since the start time will be credited to thechallenge.

6) A challenge is not expected to be changed after it is created.

Other rules, restrictions and the like may be defined and is not limitedto the above example.

Head to Head: Head to Head challenges are challenges in which theparticipants' performances are treated individually and not grouped. Theparticipants' performances may further be compared with one another todetermine a winner.

Search Challenge: Challenge search will return a list of challengeobjects based on the keyword provided. The challenge objects in the listmay be a trimmed down version of the full challenge object.

Team Up: Team Up is a challenge type that may have the following rules:

1) There are at most 2 members. Other limits may be set such as 3, 5,10, 13, 17, etc.

2) Any two (or other number of) members can have only one active teamup.

3) The challenge starts when the second person (or last person) accepts.

4) The challenge ends 72 hours after the start time.

5) If the challenge hasn't started 24 hours after it is created, itexpires.

6) The fuel amount is integer.

7) The challenge cannot be updated.

8) A person can have only 50 active team ups.

The Challenge Type can be:

Teamup Band Together Friend

1) The user selects a friend from the list of friends and creates achallenge.

2) The invitation is sent to the friend.

3) If the friend accepts the challenge the challenge becomes active.

4) Each member should reach the fuel target so the challenge can beconsidered completed.

Teamup Band Together Blind Match

1) On the blind match you select one of the preset activity pointtargets and proceed to create the challenge.

2) The system will match you with a random user taking the same type ofchallenge with the same fuel level.

3) If a match is found, the user has the right to accept or deny it.

4) If the user accepts, the start time and the end time will be updated.

5) If the user denies, both the user and the creator of the challengeare available for blind match. Basically, a separate challenge iscreated for the user.

Legacy API

Some services or functions may be defined to interface with legacysystems such as a legacy activity tracking and monitoring site orsystem.

Generate PIN Service: Retrieves a unique PIN for an empty usercontainer.

Generate Token Service: Generates a one-time-use token with which thelocal software can launch a browser to a specified website or page, andautomatically login the user. The token is one-time-use only as it ispassed in the clear over HTTP, and therefore cannot be used to hijack auser's account.

Get PIN From Token: Get PIN from a one-time access token.

Get PIN Status Service: Provides information about the user containerassociated with this PIN.

Sync Complete Service: Called to tell an activity tracking applicationthat the sync session is complete. This call may have an internal delayfor 10 s in order for this call to be the last in a group of activities.

Community

The multi-activity platform and system may further host a community ofusers seeking to track and monitor their activity levels. Communitiesmay refer to all users registered with the system or a sub-group withinthe users (e.g., a group of friends, a location based group, anorganization based group, age groups, device type groups, etc.).Accordingly, various services and functions may be provided to interactwith community functionality.

Get Community Challenge Stats Totals: This service will provide thelifetime aggregations for any community/challenge type pair. Forexample, a user may request aggregation information for challenges ofthe week within the 25-49 male community. The community may be definedbased on demographics, activity type, device type, age group, gender,location and the like and/or combinations thereof.

Get Community Leaderboard: This service will return the requestedCommunity Leaderboard. This service may cause the system to calculatethe Leaderboard, or may only return the leaderboard if alreadygenerated/present. In one example, if the Leaderboard has not beencalculated yet, an error message will be displayed. There may bemultiple types of Community Leaderboards including a Seven Day Rollingand an All Time. These two types of leaderboards can be requested foreach existing type of drill.

Get Community Stats: This service will provide an aggregation ofexisting as well as 3 new community aggregations as described below.These are example aggregations and do not represent an exhaustive list.

Community—Total/Average Fuel Today, Week, Month, Year, All Time.

Community—Average Activity Point Daily Goal for Device X users—TodayWeek, Month, Year, All Time.

Community—Total Device X Daily Goal Reached Today, Week, Month, Year,All Time.

Community—Total/Average Step: Today, This Week, This Month, This Year,All Time.

Community—Total/Average Calories: Today, This Week, This Month, ThisYear, All Time.

Community—Average Community Daily Goal.

Community—Total/Average Distance Today, This Week, This Month, ThisYear, All Time.

Community—Total/Average Calories: Today, This Week, This Month, ThisYear, All Time

Community—Total # of Users for each vertical and entire community.

Get Community Stats Frequencies: This service will provide the Historyaggregations for any community/activity pair for any frequency (e.g.,weekly, monthly, annual, etc.).

Get Community Stats Total Users: This service will provide the real timenumber of community users (e.g., all users on the site or within a morespecific community).

Get Community Stats Totals: This service will provide the lifetimeaggregations for any community/activity pair.

Get XYZ Community Leaderboard: This service will return the requestedactivity XYZ Community Leaderboard. Activity XYZ may correspond to aparticular type of activity or activities performed using a particulartype of tracking device or devices. This service may calculate theLeaderboard or might only return a leaderboard if already present. Ifthe Leaderboard has not been calculated yet, an error message may bedisplayed in some examples. There are multiple types of CommunityLeaderboards including Current Week and All Time. These two types ofleaderboards can be requested for each existing type of drill.

Get Friend Leaderboard: This service will calculate and return therequested Friend Leaderboard. There may be multiple types of leaderboardincluding Friend Leaderboards, Current Week and All Time. These twotypes of leaderboards can be requested for each existing type ofaggregation.

Get Friends Leaderboard: This service will return a Leaderboard for aspecified drill that ranks the user and his/her friends only. If theuser doesn't have any friends the leaderboard won't be shown.

Get Friends List All: This service allows a user to see a listing of alltheir friends.

Get Friends List Common: This service allows a user to see a listing offriends user has in common with another friend.

Get Friends List Most Active: This service allows a user to see alisting of the recent activity of all of a user's friends.

Get Friends List Recent Activity: This service allows a user to see alisting of most recently active friends and what they did (e.g.,activities performed, devices used, locations, etc.).

Get Friends List Team Up: This service allows a user to see a listing offriends user most recently did a team up with.

Get Activity Point Friends List Service: Returns a list of the user'sfriends with corresponding information on their activity points(cumulative level, daily level, daily goal.) The request specifiessorting by activity, cumulative activity point level, daily activitypoint level, or screen name. This service is used by applications to geta list of friends with corresponding activity point levels for a user.

Get Homepage Community Stats: Returns an object representing cumulativestats over a rolling 30 day period for the given activity type andcommunity type.

Social Share: FACEBOOK: Post/Share content to FACEBOOK that friends cansee.

Social Share: TWITTER: Post/Share content to TWITTER that friends cansee.

Test end point—Trigger Community Leader board calculations: This endpoint is used for testing purposes to trigger the calculation ofCommunity leaderboards. This is an asynchronous call which will alwaysreturn a success message. This end point will not be mapped by APOGEEand will only be available on the staging environment. There are twotypes of Community Leaderboards, Seven Day Rolling and All Time. Thesetwo types of leaderboards are calculated for each existing type ofdrill.

Device

Different devices may have different setting or setup parameters andprocedures and ways in which data is to be communicated and/or stored.Accordingly, APIs may be provided for a device to retrieve needed dataand/or to submit various types of information.

Device Settings: (GET) Retrieves a user's preferences for a specificdevice. (POST) Updates a preference for the specified User Device. UUIDrepresents the user device id.

Device Settings (Protocol X): Sets device settings to a particularprotocol such as protocol X.

Device Setup: Explanation on how devices are implemented.

When syncing a device, a device may be required to have a serial numberand type. If either of these items is not present or incorrect, theapplication may provide an error. If you are associating a group ofdevices to a user that have been synced together, then you must pass theDeviceConfigGroupId that was presented when the devices were firstsynced. Also if the individual device has been associated with a user,then the DeviceId may also be required to be passed. IfDeviceConfigGroupId is not sent when the devices are already associatedwith a user as a group, then it considers them a new group of devicesand assigns a new DeviceConfigGroupId.

Serial numbers are unique identifiers. If a device with a serial numberthat is already associated to a user is sent (without sending in theDeviceConfigGroupId or DeviceId), then the system may return an error.The error will state that this device's serial number is alreadyassociated to another user, even if you are that user.

A Type variable may be defined as the type of device that is beingassociated to the user. This variable or parameter may be required inorder for a system to know what kind of device is being associated. Ifthe device passed in has an invalid type or is empty then an error willbe thrown.

Devices that have not been grouped together before are considered a newgroup of devices. If two devices that have already been associated witha user with a brand new device are grouped, this association mayconstitute a new device group. Because this represents a new group ofdevice, a DeviceConfigGroupId is not required in the communication. TheDeviceIds for the old devices that have already been associated with theuser may be passed to the system. When the devices are synced, a newDeviceConfigGroupId and a new Device Id may be returned.

For a first sync for new devices: devices with an unused serial numbermay be sent to the system without a DeviceId or DeviceConfigGroupId. TheDeviceConfigConfigId will be returned along with each DeviceId for eachof the devices in the order that they were passed/communicated.

For any sync after the first with the same devices: the devices'DeviceIds and the DeviceConfigGroupId are transmitted/communicated. Thesame DeviceConfigGroupId will be returned back, but not the DeviceIds.

For any sync after the first sync with new devices along with olddevices: DeviceIds for the old devices are communicated withoutDeviceIds for new devices. In some arrangements, a DeviceConfigGroupIdmight not be sent since this will be a new group of devices. The newDeviceConfigGroupId will be returned to be used for future syncs ofthese devices. The DeviceId's of the new devices will be returned also.

Phone Device Settings (Protocol X): Sets Phone device settings to aparticular protocol such as protocol X. This may also allow the deviceto know what protocol is to be used to communicate with themulti-activity platform.

Reset Device: Sets the User Device “delete_ind” flag to true. UUIDrepresents the device id.

Reset LastSyncOffset and LastSyncTimestamp: Sets the device'sLastSyncOffset and LastSyncTimestamp to the given values.

Retrieve, Add or Update Device: (GET) Retrieves a user device record orrecords. (POST/PUT) Adds or updates a user device record. UUIDrepresents the user device id, returned in both the POST and the PUTresponse body.

Fitness/Workout Programs

Activity data recorded during a user's performance of a fitness orworkout program may be communicated in accordance with variouspredefined functions and services.

Fitness: Get Pending Program Data: Retrieves all pending days in aworkout program. Searches for existing workout programs by requestedprogram ID. Returns a list of all pending days or workout sessions inthe program.

Fitness: Post Program Data Capture: Adds program data into the systemagainst a console post. If the program data already exists for thesupplied program id, update the changes.

Fuel Balance Service: Retrieve the activity point balance for a user.This service is designed for experiences that need to show a user'sactivity point balance.

Get Activity Point Level Service: Gets the cumulative activity pointlevel for specified time period. If no start time and end time specifiedthe service will respond with activity points earned for a current day.

Goals—Achievements

As noted herein, users may reach achievements based on their physicalactivity. Achievements may be reached based on cumulative activitypoints, activity points for a predefined time period (e.g., less thanlifetime), average activity points per time period, other metrics andthe like.

Acknowledge Achievement By Achievement Id: Acknowledges that a user hasseen an achievement. This service will serve as a way of indicatingwhether the user has triggered the ‘OK/CONFIRM’ on an achievementsignifying that they have acknowledged the achievement. For example,once a user has acknowledged the achievement, the achievement might notbe automatically displayed or provided to the user again. The user maystill view or access the achievement by manually retrieving theachievement.

Acknowledge Achievement By Activity Id: Acknowledges that a user hasseen all achievements associated with an activity. This service willserve as a way of indicating whether the user has triggered the‘OK/CONFIRM’ on an achievement signifying that they have acknowledgedthe achievement.

Add Goal Resolution: Adds a goal resolution against the supplied goalid. If the goal resolution already exists for the supplied goal id, itwill not add the resolution.

Copy Goal: This service is used to copy a goal for the user based on thegoal associated with goalId.

Create Goal: This service is used to create a goal for the user.

Get Achievements List: Return a list of the user's achievements.

Update and Delete Goal: Update Goal: This service is used to update agoal for the user.

Delete Goal: This service is used to delete a goal for the user.

User Registration/Initiation

The below services and functions may be used to register a user to anactivity monitoring system

Link: Link existing user based on User Id (nuid) with an externalnetwork such as FACEBOOK or TWITTER.

Login: This service is used by applications to login a user to theactivity monitoring service or system. On login, an oauth (e.g.,authentication) access token is provided back to the calling applicationthat can be used for further calls that need login enabled. Externalnetwork name can be supplied to login using third-party authentication.The system may proxy these login requests to the appropriate externalnetworks.

Pin Request for Access Token: Gets the API access token and refreshtoken based on the DIN (Device Identification Number) that is passed.

Pin Request for Imprint: Adds a device. This will create and return aDIN (Device Identification Number) for the device.

Pin Request for Is Logged In: Checks if the user is already logged in ornot.

Pre Registration Check: Check if the supplied email address and systemscreen name are available for a new registration. This service is usefulfor any application about to register a user with the system. Thisservice is invoked prior to registration to check if the email address,screen name/tag name, dobType and dob, and locale already available withthe application can be used to register the user with the system.

Register: Register user with the supplied information. This service isused by applications to register a user with the activity system.

Token Request Service: This service might only be called by a softwareapplication to get a one-time token during the initiation/imprint flowwith a DIN (Device Identification Number).

User Initiation Statistics: Returns initiation statistics if theinitiation period has not ended; returns initiation result if theinitiation period has ended. The initiation period may be, for example,a first 24 hours in which the user is to perform an average day's worthof activity. During the initiation period, this service will respondwith the current metrics or statistics of user activity. After theinitiation period, this service will respond with the final metrics orstatistics accumulated during the initiation period. In a particularexample, when the service is called, a start_time_local parameter isloaded, and the end time of initiation period is calculated. The endtime is then checked against the current time to determine if we arestill in the initiation period. If so, the values of relevant columns(e.g., requested activity metrics) are returned along with a status code1. If the initiation period has ended, check SYNC_DATE (e.g., a datewhen data was last synchronized) with the end time. If SYNC_DATE is pastthe end time, indicating data for the initiation period is up to dateand ready, the status code is set to 0. Otherwise the status code is setto 2. Additionally, the values of relevant columns are returned. Belowis an example table of status codes.

Status Description 0 All the values are ready 1 The initiation is inprogress 2 The initiation period has ended, but not all the values areready

Activity Service Layer

Interfaces for the activity service layer may be used to handle alllogin, registration and social network/community integration.

Activity List Service: Get activity List back based on the type passedin.

Create User Service: Creates a new user through the activity monitoringsystem or third party provider. User gets automatically logged in afterregistering a user successfully. During third party login, thenewly-created UPM id will be fed into the third party provider.Additionally “partner” parameters can be passed in to set partnernetwork settings to be attached to the user. This creates anothernetwork entry for a “Partner” with the network name as specified in theservice call, the unique id of that user and the screen name.

If the user is passing “Partner” parameters to store for the user thefollowing fields are required in order for the partner information to besaved. Partner data not saving might not prevent the service fromcontinuing normally.

partnerGuid

partnerNetwork

partnerScreenName

Crop Profile Image of a User: Crops and uploads the profile image of auser to permanent location

Delete Profile Image of a User: Deletes the profile image of a user(soft delete)

Email Content Service: This service gets the content of an email basedon app, locale, type. The user sends in the number of invitation linksto be created. The service implementation will get the content for afriend invitation from a specific user and a list of links (i.especified by the count).

External Network Friend List Service: Get a list of the user's friendsin an external network. Mutual friends can be excluded from the list ifan additional parameter is passed in with the request.

External Network List Service: Returns the list of external networkssupported by the activity monitoring service.

External Network User Check Service: This service checks to see if anexternal network user already exists in the system or not. This servicewill perform the following based on the value of action:

1. Given an external network user's unique ID, e.g., FACEBOOK user ID,the service may return an UPM ID if the user exists in the system and islinked to the external network user.

2. If there is no record found, then the service may try to match basedon email provided by the caller. If there is a matching email, theservice will link the external network user record with the existing UPMrecord with a new link type and return the upm id. Additionally theservice will also setup the user to login using, e.g., FACEBOOK OAuthtoken or FACEBOOK credentials (email/pwd registered with FACEBOOK).

3. If the above two checks do not result in a match, create a new emailonly user with the information provided by the caller and link it to theexternal network.

action=check-->point 1 above

action=link-->points 1 and 2 above

action=createAndLink-->all of the above

Friend Create Service: Sends a friend request invitation to anotheruser, or accepts a pending one.

Friend External Create Service: Sends a friend request invitation to anyexternal user (not a user of the activity monitoring service) via email.

Get User Security Status Service: Retrieves a user's security statusbased on the cookie sent and returns the user's security level. Thesecurity level is retrieved from the slCheck cookie and theAnalysisUserId cookie, depending on whether or not the user is loggedin.

Get User Service: Returns core User profile data. User data is held inUPM service and this service provides a single view into user profile.It will also return the extended User profile information from socialsite. If this is called anonymously, a limited subset of data will bereturned based on the requested user's privacy status.

Is Logged In Service: Checks if the current user is logged in andreturns security level of user if user is logged in. It is necessary fora user to be logged in in order to use the NSL services.

Login Service: Authenticates the user credentials to allow the user tologin. A user can choose to login using their system credentials orcredentials registered with any other external networks like Facebook,Twitter, etc. An activity monitoring service uses the User ProfileManagement (UPM) service to register and maintain a user profile. It mayalso use any authentication provider like Facebook, Twitter (hereafterreferred to as 3PP or third party providers or external network). Onsuccessful login, it provides authorization cookies required to makesubsequent calls to NSL.

An additional useful feature is “remember me”. It is sent as an optionalparameter in the login request. This will allow the user to be logged inuntil he/she explicitly signs out of the application. Currently, theduration of validity for “remember me” is set as 30 days.

Also a user may login using oAuth access token when the user is alreadylinked to some external network. Along with their credentials, users cansend partner network information and it will be stored in the database.This information is not validated by NSL. When a user passes in“Partner” parameters, the partner's network settings will be attached tothe user. This in turn creates a new network entry for that “Partner”with the network name as specified in the service call.

Logout Service: Logs the user out from the NSL.

Mark as Read Notification Service: Sets a specified notification'sstatus to ‘read’.

Team Activity List Service: Get team activity List back. Team activitiescan be filtered based on titleId or app or both.

Upload Profile Image of a User: Uploads the profile image of a user totemporary location

User Activity List Service: Get user activity List back based on thefilter criteria passed in. User activities can be filtered based ontitleId or app or both. This service also returns activities of any userbased on the userId passed in.

User Email Check: This service checks if the email has already been usedin creating an account. Since email is an unique identifier, therecannot be multiple users registered with the same email.

User External Network Link: This service will link the FB/Twitter/otherexternal network login with the existing account. This service will alsoallow linking through another Social Network.

User Forgot Password: This service helps the user reset their passwords.The service will accept an email and check that a user exists with thatemail address and sends to that address a temporary password reset URLemail. The email contains a unique one time use reset key. The user'spassword is not reset until the user actually uses the reset key toreset the password meaning the act of sending a password reset emailalone will not reset the user's password.

User Friend Activity List Service: Get user's friends activity List backbased on the filter criteria passed in. User's friend activities can befiltered based on titleId or app or both. This service also returnsactivities of any user's friend based on the userId passed in.

User Friend List Service: Get User Friend List along with friends basicdetails.

User Friends Match Service: Gets user email details (passed by thecaller of the service) if that email matches/exists in the system.Mutual friends can be excluded from this list if an additional parameteris passed in with the request.

User Screen Name Check: This service checks if the screen name the useris intending to take already exists or not. Since a screen name is aunique identifier there cannot be multiple users with the same screenname.

User Search: Searches for a user based on a searchstring passed in.

User Workout Cheer List Service: This service returns all the cheers(likes and comments) posted for a user's workout from an external socialnetwork (Facebook).

User Workout Create Service: Create a user Workout. Multiple workoutscan be created (maximum 10).

User Workout Finish Service: This service lets a user post a message toan external social network (ex. Facebook) indicating the finish of theirWorkout and their desire to have friends cheer them on.

User Workout List Service: Get the list of user workouts.

User Workout Start Service: This service lets a user post a message toan external social network (Facebook) that indicates the start of theirWorkout and their desire to have friends cheer them on.

Synchronization

Synchronization between an activity monitoring device, a multi-activityplatform system and/or an application may be facilitated through thefollowing APIs.

Get Server Time: Get the current GMT time of the multi-activity platformservers.

Last Date and Time Sync Service: Returns the date and time of the lastsync based on the AppId (e.g., an application identifier). This serviceis useful for any application/device that needs to know the last timewhen the device synchronization occurred and know if there are new itemsto synchronize.

Last Sync LSO (Last Sync Offset) and LSTS (Last Sync Timestamp)—Thisservice is used to get the last LSO (Last Sync Offset) and LSTS (LastSync Timestamp) back as user does a sync on the device.

Last Sync Service: This service is to get the last sync details. Userlogin and get the last sync detail by hitting the endpoint. This serviceis used to get the last sync delta back as user does a sync on thedevice.

Sync Service (Basketball): Syncs basketball user activities to anactivity monitoring service back end.

Sync Service (Device X): This service is useful for any applicationwishing to sync user's activities between a particular device such asDevice X and an activity monitoring service back end. The actual metricsbeing synced will have to be negotiated with the activity monitoringservice for an optimal user experience.

Sync Service (Running): Syncs running user activities to an activitymonitoring service back end. This service is useful for any applicationwishing to sync user's activities to an activity monitoring servicebackend. The actual metrics being synced will have to be negotiated withactivity monitoring service for optimal User experience.

Sync Service (Device Y): Syncs user activities between anotherparticular device such as Device Y to an activity monitoring serviceback end.

Sync Service (Training): Syncs training user activities to an activitymonitoring service backend.

Sync Service (Fitness/Workouts): Syncs fitness/workout program useractivities to an activity monitoring service backend.

Sync Service v2.0: Syncs user activities to an activity monitoringservice back end.

Sync Status: Get the status of the recent sync activity, indicating ifthe back end processing is complete.

User-Oriented Information, Events and Settings

Various services and functions may be defined for defining, configuring,sharing and retrieving user profile information. Additionally, userevents may be communicated using various API services. User events mayinclude reaching activity goals, reaching various activity achievements,warnings messages, workout reminders, other alerts and the like.

Create Event Service: Send a user event to the event service. Thisservice is useful for any application wishing to send a user event to bedisplayed on a user's home page or landing page of his or her account.

Delete Event Service: Send a user event to the event service. Thisservice is useful for any application wishing to send and delete a userevent to be displayed on a user's home page or landing page of his orher account.

Delete User Data: This perform a hard-delete of user data. Cache datawill also be cleared. Response should be success or failure. Forexample, user data on any number of protocol-compliant devices includinga multi-activity system, an activity monitoring device, an intermediarydevice and the like may be deleted in this manner.

Get and Update Privacy: Get information about the authenticated user'sprivacy settings. Update the authenticated user's privacy settings. Anyuser that uses the multi-activity platform has a profile in themulti-activity system. The GET version of this service returns theprofile privacy setting associated with the authenticated user.

Get Athlete Information: Return information about an athlete.

Get Drill: Return the drill information.

Get Drill Metadata: This service will be used periodically to get drillmetadata from the multi-activity system. The drill metadata is a list ofprepared drills and their associated properties.

Get Friends Me Profile: Get information about the authenticated user'sfriend's ME profile. Any user that uses the multi-activity platform hasa profile in the multi-activity system. The GET version of this servicereturns all the profile information associated with the authenticateduser. The “Friend's” upmId should be passed through the url.

Get Insights: Get a list of insights on a user, based on a rule basedsystem. It is possible that no insights are returned. Insights mayinclude recommendations for the user, identification of areas forimprovement, words of encouragement and the like.

Get Me Profile: Get information about the authenticated user's MEprofile. Any user that uses the multi-activity platform has a profile inthe multi-activity system. The GET version of this service returns allthe profile information associated with the authenticated user.

Get Me Profile Basketball: Get basketball information about theauthenticated user's ME profile. Any user that uses the multi-activityplatform has a profile in the multi-activity system. The GET version ofthis service returns all the profile information associated with theauthenticated user.

Get Me Profile Training: Get training information about theauthenticated user's ME profile. Any user that uses the multi-activityplatform has a profile in the multi-activity system. The GET version ofthis service returns all the profile information associated with theauthenticated user.

Get Me Profile User Header: Get information about the authenticateduser's Header information. The GET version of this service returns allthe profile information associated with the authenticated user.

Get Mobile App Summary: Returns the user's profile data, lifetimetotals, achievements, and last 30 activities for the appid given in therequest header. For example, different application may be configured toconsume or detect different activities. Accordingly, only thoseactivities consumable by the application identified by the appid may bereturned.

Get Multi-Activity Profile: Get information about the authenticateduser's multi-activity profile. Any user that uses the multi-activityplatform has a profile in multi-activity system. The GET version of thisservice returns all the profile information associated with theauthenticated user across all verticals. If a specific mobileapplication (for example Basketball) is calling the multi-activityprofile, then the calling application's specific records are returned inthe response. In some arrangements, the sorting of the returned recordsmust be done by the calling application.

Get Profile and Update Profile: Get information about the authenticateduser's profile. Update the profile of the authenticated user. The PUTversion of this service will update the profile with the providedinformation. If an item is included in the request body, the value ofthe item will be updated; if the value is null, the item will beremoved. If an item is not included in the request body, it will beignored. However, if the item is required, an error will be thrown. Thisservice might not update a UPM database. The GET version of this servicereturns all the profile information associated with the authenticateduser.

Get Trainers and Athletes Metadata Information: Return the list of allathletes/trainers/celebs along with their details.

Initial Assessment: Login the user into the multi-activity system.

List Athletes: Return a list of athletes.

List Drills: Returns a list of drills.

Post Athlete Information: Post athletes' information to multi-activitysystem back end.

Post Drill Information: Post information about a drill to themulti-activity system backend.

Update Event Service: Send a user event to the event service. Thisservice is useful for any application wishing to send and update a userevent to be displayed on the home page.

Utilities

Cache Clearing Service: Clears the specified cache.

Cache Refresh Service: Posts a request to refresh the cache with aspecific entity.

Event Service: Creates/Updates/Deletes an event to the Unified EventStream (UES).

Activity Multiplier Service: Retrieve the fuel multiplier for a givenfuel source.

Get Calendar: Return list of user events & user goals to be displayed onthe Calendar.

Get Notifications: This service is used to get notifications. The GETreturns a list of notifications based upon the request type.

List Supported External Networks: Return a list of supported networksfor login to the activity monitoring service/community. The activitymonitoring service/community itself may be returned as a possiblenetwork that can be used for login. Image formats can be returned ineither JPG or PNG format.

List Supported Locales: Returns a list of supported locales andcorresponding age limits for login to the activity monitoringsystem/service. This service is useful for any application wishing topass locale information during registration, to query and obtain thelist of locales supported by the system/service and the correspondingage limits.

Manual Share: Retrieves a Manual Share record of a user.

Notification Preferences 1.0: (POST) This service is used to add thenotification preferences of a user to the activity monitoringsystem/service. (GET) This service is used to get the notificationpreferences of a user.

Notification Preferences 2.0: (POST) This service is used to add thenotification preferences of a user to the activity monitoringsystem/service. (GET) This service is used to get the notificationpreferences of a user.

Refresh Device Token 1.0: When an application (e.g., a mobileapplication) wants to use push notifications, it must call this serviceevery time it is opened in order to keep the device token assigned bythe mobile device (which can change over time) up to date on thebackend.

Refresh Device Token 2.0: When an application wants to use pushnotifications, it must call this service every time it is opened inorder to keep the device token assigned by the mobile device (which canchange over time) up to date on the backend.

Remove Device Token 1.0: When a smart phone (e.g., iPhone) applicationturns off push notifications or unlinks the user account on the device,it must call this service to remove the record of that device token fromthe backend.

Remove Device Token 2.0: When a smart phone (e.g., iPhone) applicationturns off push notifications or unlinks the user account on the device,it must call this service to remove the record of that device token fromthe backend.

Server Time Request: Get the current GMT time of the multi-activityservers.

Time Zone Ids: Gets a list of valid time zone ids.

CONCLUSION

While many of the aspects and features described herein relate toactivity, similar processes, functions, systems and the like may beapplied to inactivity. For example, a monitoring device may beconfigured to detect inactivity and such information may also besynchronized or otherwise transmitted to a multi-activity platform andsystem to affect a user's activity level and profile. In some examples,inactivity may be determined by the multi-activity platform and systemto determine an amount of activity points that are to be deducted as aresult of the inactivity.

Additionally, while the invention has been described with respect tospecific examples including presently preferred modes of carrying outthe invention, those skilled in the art will appreciate that there arenumerous variations and permutations of the above described systems andmethods. For example, various aspects of the invention may be used indifferent combinations and various different subcombinations of aspectsof the invention may be used together in a single system or methodwithout departing from the invention. In one example, software andapplications described herein may be embodied as computer readableinstructions stored in computer readable media. Also, various elements,components, and/or steps described above may be changed, changed inorder, omitted, and/or additional elements, components, and/or steps maybe added without departing from this invention.

1-29. (canceled)
 30. A method performed by an athletic tracking systemcomprising: receiving physical activity data from a plurality ofactivity monitoring devices, each activity monitoring device including asensor configured to measure physical activity data of a user;categorizing the received physical activity data based on type ofactivity monitoring device; storing, in a first storage area, a firstportion of the physical activity data corresponding to a first type ofactivity monitoring device; storing, in a second storage area, a secondportion of the physical activity data corresponding to a second type ofactivity monitoring device; determining, based on the first type ofactivity monitoring device, a first synchronization offset configured tospecify a point at which synchronization of the first portion of thephysical activity data is to begin; and determining, based on the secondtype of activity monitoring device, a second synchronization offsetconfigured to specify a point at which synchronization of the secondportion of the physical activity data is to begin; and displaying, by adisplay unit, a synchronized data display including the first portion ofthe physical activity data modified by the first synchronization offsetand the second portion of the physical activity data modified by thesecond synchronization offset.
 31. The method of claim 30, furthercomprising: determining a third synchronization offset for the firststorage area; and determining a fourth synchronization offset for thesecond storage area, wherein the synchronized data display includesphysical activity data from the first storage area modified by the thirdsynchronization offset and physical activity data from the secondstorage area modified by the fourth synchronization offset.
 32. Themethod of claim 30, further comprising: categorizing the receivedphysical activity data based on type of physical activity; storing, inthe first storage area, a portion of the physical activity datacorresponding to a first type of physical activity performed; andstoring, in a second storage area, a portion of the physical activitydata corresponding to a second type of physical activity performed. 33.The method of claim 30, further comprising: generating a first set ofmetrics for the first portion of the received physical activity data;and generating a second set of metrics for the second portion of thereceived physical activity data, wherein the first set of metricsincludes at least one activity metric not included in the second set ofmetrics.
 34. The method of claim 30, further comprising: determining afirst type of activity associated with a portion of the receivedphysical activity data; determining a first predefined set of activitytags used for the first type of activity; and processing the portion ofthe received physical activity data to extract one or more values forthe first predefined set of activity tags.
 35. The method of claim 34,further comprising: determining a second type of activity associatedwith another portion of the received physical activity data; determininga second predefined set of activity tags used for the second type ofactivity; and process the other portion of the received physicalactivity data to extract one or more values for the second predefinedset of activity tags.
 36. The method of claim 30, further comprising:determining a number of activity points earned by the user based on thereceived physical activity data; and categorizing the determined numberof activity points based on the at least one of: type of activitymonitoring device used and type of physical activity performed.
 37. Themethod of claim 30, further comprising determining whether the user hasachieved a streak of two or more consecutive goal time periods in whicha corresponding activity point goal has been reached.
 38. The method ofclaim 30, further comprising recommending at least one of a product andan athletic activity based on the received physical activity data. 39.The method of claim 30, further comprising: processing a challengebetween a first user and a second user; receiving a first set ofphysical activity data from the first user; receiving a second set ofphysical activity data from the second user; and determining a winner ofthe challenge based on the first and second sets of physical activitydata.
 40. A method performed by an athletic tracking system comprising:receiving physical activity data from at least one activity monitoringdevice including a sensor configured to measure physical activity dataof a user, wherein the received physical activity data includes physicalactivity data for a plurality of types of physical activity;categorizing the received physical activity data based on a type ofphysical activity performed; determining a first synchronization offsetfor a first portion of the physical activity data corresponding to afirst type of physical activity performed, the first synchronizationoffset specifying a point at which synchronization of the first portionof the physical activity data is to begin; determining a secondsynchronization offset for a second portion of the physical activitydata corresponding to a second type of physical activity performed, thesecond synchronization offset specifying a point at whichsynchronization of the second portion of the physical activity data isto begin; and displaying, by a display unit, a synchronized data displayincluding the first portion of the physical activity data modified bythe first synchronization offset and the second portion of the physicalactivity data modified by the second synchronization offset.
 41. Themethod of claim 40, further comprising: storing, in a first storagearea, a third portion of the physical activity data; storing, in asecond storage area, a fourth portion of the physical activity data;determining a third synchronization offset configured to specify asynchronization point for the first storage area; determining a fourthsynchronization offset configured to specify a synchronization point forthe second storage area; and wherein the synchronized data displayincludes the third portion of the physical activity data modified by thethird synchronization offset and the fourth portion of the physicalactivity data modified by the fourth synchronization offset.
 42. Themethod of claim 41, wherein the first storage area is associated with afirst type of activity monitoring device and the second storage area isassociated with a second type of activity monitoring device.
 43. Themethod of claim 42, further comprising: synchronizing the fourth portionof the physical activity data with a device of the second type ofactivity monitoring device; and updating at least one of the firstsynchronization offset and the second synchronization offset withoutmodifying the fourth synchronization offset.
 44. The method of claim 40,wherein the first portion of the physical activity data corresponds todata recorded using a first type of activity monitoring device, andwherein the second portion of the physical activity data corresponds todata recorded using a second type of activity monitoring device.
 45. Amethod performed by an athletic tracking system comprising: storing, ina first storage area, a first portion of physical activity data receivedfrom a sensor configured to measure physical activity data of a user,the first portion of physical activity data corresponding to a firsttype of physical activity performed; storing, in a second storage area,a second portion of the physical activity data received from a sensorconfigured to measure physical activity data of a user, the secondportion of the physical activity data corresponding to a second type ofphysical activity performed; defining a first data offset forsynchronizing the first portion of the physical activity data associatedwith a first device; defining a second data offset for synchronizing thefirst portion of the physical activity data associated with a seconddevice; defining a third data offset for synchronizing the secondportion of the physical activity data associated with the first device;defining a fourth data offset for synchronizing the second portion ofthe physical activity data associated with the second device; responsiveto receiving an instruction to synchronize data with the first device,modifying the physical activity data such that the first portion of thephysical activity data is modified by the first data offset and thesecond portion of the physical activity data is modified by the thirddata offset; and displaying, by a display unit, a synchronized datadisplay including the modified physical activity data synchronized withthe first device.
 46. The method of claim 45, further comprising:responsive to receiving an instruction to synchronize data with thesecond device, modifying the physical activity data such that the firstportion of the physical activity data modified by the second data offsetand the second portion of the physical activity data modified by thefourth data offset; and displaying, by a display unit, a synchronizeddata display including the modified physical activity data synchronizedwith the second device.
 47. The method of claim 45, further comprising:determining whether the first data offset is greater than the seconddata offset; and in response to determining that the first data offsetis greater than the second data offset, updating the second data offsetto equal the first data offset.
 48. The method of claim 45, furthercomprising: determining that the first device has synchronized the atleast a portion of the physical activity data with the second device;and in response to determining that the first device has synchronizedthe at least a portion of the physical activity data with the seconddevice, updating the second data offset.
 49. The method of claim 45,further comprising: providing a visualization to at least a portion ofthe display unit of the received physical activity data, whereindifferent visualizations are provided depending on the at least one of atype of activity monitoring device used and the type of physicalactivity performed.